Report OTLP export status in startup log by bm1549 · Pull Request #6096 · DataDog/dd-trace-rb

bm1549 · 2026-07-24T01:35:50Z

What does this PR do?

Adds three boolean fields to the CORE section of the "DATADOG CONFIGURATION" startup log (lib/datadog/core/diagnostics/environment_logger.rb):

otlp_traces_export_enabled is a constant false: Ruby has no OTLP trace exporter, and OTEL_TRACES_EXPORTER=otlp is unsupported, so spans are always sent to Datadog in the native format.
otlp_metrics_export_enabled reflects Datadog.configuration.opentelemetry.metrics.enabled (DD_METRICS_OTEL_ENABLED).
otlp_logs_export_enabled reflects Datadog.configuration.opentelemetry.logs.enabled (DD_LOGS_OTEL_ENABLED).

Specs and the RBS signature are updated to cover the new fields.

Motivation:

Part of a cross-tracer effort to report OTLP export status in the startup log using identical JSON keys across the dd-trace-* libraries.

Change log entry

None.

Additional Notes:

The metrics and logs values read from the opentelemetry settings namespace through a defensive helper, so a missing namespace reports false instead of raising.

How to test the change?

Covered by spec/datadog/core/diagnostics/environment_logger_spec.rb, which asserts the default state (all false), the metrics-enabled and logs-enabled cases, and the fallback when the opentelemetry namespace is unavailable.

Related PRs — cross-tracer OTLP startup-log effort

dd-trace-js: feat(startup-log): report OTLP export status dd-trace-js#9517
dd-trace-py: feat: report OTLP export status in startup log dd-trace-py#19265
dd-trace-java: Report OTLP export status in tracer startup log dd-trace-java#12062
dd-trace-dotnet: Report OTLP export status in tracer startup log dd-trace-dotnet#8936
dd-trace-rb: Report OTLP export status in startup log #6096
dd-trace-go: feat(tracer): report OTLP export status in startup log dd-trace-go#5062
dd-trace-php: feat(tracing): report OTLP export status in startup log dd-trace-php#4056
system-tests: Cover OTLP export status in startup logs [dotnet@brian.marks/otlp-export-startup-log][nodejs@brian.marks/otlp-export-startup-log][python@brian.marks/otlp-export-startup-log][ruby@brian.marks/otlp-export-startup-log] system-tests#7376
Related dd-trace-py fix (OTLP logs self-export loop, surfaced by this work): fix(opentelemetry): prevent OTLP logs self-export loop dd-trace-py#19266

Report whether the tracer exports each telemetry signal over OTLP in the "DATADOG CONFIGURATION - CORE" startup log via three boolean fields: otlp_traces_export_enabled (always false; Ruby has no OTLP trace exporter), otlp_metrics_export_enabled, and otlp_logs_export_enabled. The metrics and logs values read from the opentelemetry settings namespace, accessed defensively so an unregistered namespace defaults to false. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

dd-octo-sts · 2026-07-24T01:36:16Z

Typing analysis

Note: Ignored files are excluded from the next sections.

Untyped methods

This PR introduces 2 untyped methods and 1 partially typed method, and clears 2 untyped methods. It increases the percentage of typed methods from 68.16% to 68.17% (+0.01%).

Untyped methods (+2-2)

❌ Introduced:

sig/datadog/core/diagnostics/environment_logger.rbs:40
└── def self.opentelemetry_settings: () -> untyped
sig/datadog/core/diagnostics/environment_logger.rbs:41
└── def self.hash_serializer: (untyped h) -> untyped

✅ Cleared:

sig/datadog/core/diagnostics/environment_logger.rbs:20
└── def self.collect_config!: () -> { date: untyped, os_name: untyped, version: untyped, lang: untyped, lang_version: untyped, env: untyped, service: untyped, dd_version: untyped, debug: untyped, tags: untyped, runtime_metrics_enabled: untyped, vm: untyped, health_metrics_enabled: untyped }
sig/datadog/core/diagnostics/environment_logger.rbs:37
└── def self.hash_serializer: (untyped h) -> untyped

Partially typed methods (+1-0)

❌ Introduced:

sig/datadog/core/diagnostics/environment_logger.rbs:20
└── def self.collect_config!: () -> { date: untyped, os_name: untyped, version: untyped, lang: untyped, lang_version: untyped, env: untyped, service: untyped, dd_version: untyped, debug: untyped, tags: untyped, runtime_metrics_enabled: untyped, vm: untyped, health_metrics_enabled: untyped, otlp_traces_export_enabled: bool, otlp_metrics_export_enabled: bool, otlp_logs_export_enabled: bool }

If you believe a method or an attribute is rightfully untyped or partially typed, you can add # untyped:accept on the line before the definition to remove it from the stats.

datadog-prod-us1-4 · 2026-07-24T01:53:04Z

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: 543d2a6 | Docs | Datadog PR Page | Give us feedback!}

pr-commenter · 2026-07-24T02:00:38Z

Benchmarks

Benchmark execution time: 2026-07-24 02:00:36

Comparing candidate commit 0d0274b in PR branch brian.marks/otlp-export-startup-log with baseline commit e12d786 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 48 metrics, 1 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

🟩 = significantly better candidate vs. baseline
🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:tracing - trace.to_digest - Continue

unstable throughput [-1451.996op/s; +1629.344op/s] or [-4.973%; +5.580%]

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0d0274b526

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-24T21:43:59Z

+
+          # @return [Boolean] whether the tracer exports metrics over OTLP
+          def otlp_metrics_export_enabled
+            !!opentelemetry_settings&.metrics&.enabled


Honor disabled metrics exporter in startup status

When DD_METRICS_OTEL_ENABLED=true is combined with OTEL_METRICS_EXPORTER=none, this reports otlp_metrics_export_enabled: true, but the metrics integration explicitly skips adding an OTLP reader in that configuration (lib/datadog/opentelemetry/metrics.rb's configure_metric_reader returns when the exporter is none). The startup log is therefore misleading for a supported way to disable metrics export, so this should also require opentelemetry.metrics.exporter != "none".

Useful? React with 👍 / 👎.

chatgpt-codex-connector · 2026-07-24T21:43:59Z

+
+          # @return [Boolean] whether the tracer exports logs over OTLP
+          def otlp_logs_export_enabled
+            !!opentelemetry_settings&.logs&.enabled


Honor disabled logs exporter in startup status

When DD_LOGS_OTEL_ENABLED=true is combined with OTEL_LOGS_EXPORTER=none, this still reports otlp_logs_export_enabled: true, even though Datadog::OpenTelemetry::Logs#configure_log_record_processor returns without configuring an OTLP processor for that exact setting. For that supported disabled-exporter configuration, the new startup field should be false rather than only reflecting the top-level enable flag.

Useful? React with 👍 / 👎.

Report otlp_metrics_export_enabled and otlp_logs_export_enabled as false when the signal's exporter is set to "none" (OTEL_METRICS_EXPORTER=none / OTEL_LOGS_EXPORTER=none). The OpenTelemetry metrics and logs configuration skips adding the OTLP reader/processor for that value even when the signal is enabled, so the startup diagnostic log should report export as disabled. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

bm1549 added the AI Generated Largely based on code generated by an AI or LLM. This label is the same across all dd-trace-* repos label Jul 24, 2026

dd-octo-sts Bot added the core Involves Datadog core libraries label Jul 24, 2026

bm1549 marked this pull request as ready for review July 24, 2026 21:38

bm1549 requested a review from a team as a code owner July 24, 2026 21:38

chatgpt-codex-connector Bot reviewed Jul 24, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Report OTLP export status in startup log#6096

Report OTLP export status in startup log#6096
bm1549 wants to merge 2 commits into
masterfrom
brian.marks/otlp-export-startup-log

bm1549 commented Jul 24, 2026 •

edited

Loading

Uh oh!

dd-octo-sts Bot commented Jul 24, 2026

Uh oh!

datadog-prod-us1-4 Bot commented Jul 24, 2026 •

edited by datadog-datadog-prod-us1-2 Bot

Loading

Uh oh!

pr-commenter Bot commented Jul 24, 2026

Explanation

More details about the CI and significant changes

Unstable benchmarks

scenario:tracing - trace.to_digest - Continue

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Jul 24, 2026

Uh oh!

chatgpt-codex-connector Bot Jul 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

bm1549 commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Related PRs — cross-tracer OTLP startup-log effort

Uh oh!

dd-octo-sts Bot commented Jul 24, 2026

Typing analysis

Untyped methods

Uh oh!

datadog-prod-us1-4 Bot commented Jul 24, 2026 • edited by datadog-datadog-prod-us1-2 Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pr-commenter Bot commented Jul 24, 2026

Benchmarks

Explanation

More details about the CI and significant changes

Unstable benchmarks

scenario:tracing - trace.to_digest - Continue

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jul 24, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot Jul 24, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

bm1549 commented Jul 24, 2026 •

edited

Loading

datadog-prod-us1-4 Bot commented Jul 24, 2026 •

edited by datadog-datadog-prod-us1-2 Bot

Loading